Everything Totally Explained


Ask & we'll explain, totally!
Service (systems architecture)
Totally Explained


  FOR SALE!Either this or the left-hand panel are available for just $19.95 per
day, or you can have both for only $34.95! Contact us for details.  


View this entry using RSS

Everything about Service Systems Architecture totally explained

In the context of Enterprise architecture, Service-orientation, and Service-oriented architecture, the term service refers to a discretely defined set of contiguous and autonomous business or technical functionality. OASIS (organization) defines service as "a mechanism to enable access to one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description."

Service Engineering

An Enterprise Architecture Team will develop the organization’s “Service” model first by defining the top level Business Functions. Once the Business Functions are defined they're decomposed into “Services” which represent the processes and activities needed to manage the assets of the organization in their various states. An example here would be the decomposition of the Business Function “Manage Orders” into “Services” such as “Create Order”, “Fulfill Order”, “Ship Order”, “Invoice Order”, “Cancel/Update Order”, etc.

Service Description / Specification

A “Service” has a description or specification. This description consists of:
  1. An explicit and detailed narrative definition supported by a low (but not detailed [notimplementation specific]) level process model. The narrative definition is in some cases augmented by machine-readable semantic information about the service which facilitates service mediation and consistency checking of an Enterprise Architecture.
  2. A set of performance indicators that address measures/performance parameters such as availability (when should members of the organization be able to perform the function), duration (how long should it take to perform the function), rate (how often will the function be performed over a period of time), etc.
  3. A linkage to the organization’s information model showing what information the “Service” owns (creates, reads, updates, and deletes) and which information it references and is owned by other “Services”.
  4. A listing of known downstream consumers (other “Services” that depend upon its function or information) and the documentation of their requirements.

Service Implementation

A Web service provides one way of implementing the automated aspects of a given business or technical service.

Further Information

Get more info on 'Service Systems Architecture'.


External Link Exchanges

Do you know how hard it is to get a link from a large encyclopaedia? Well we're different and will prove it. To get a link from us just add the following HTML to your site on a relevant page:

    <a href="http://service__systems_architecture.totallyexplained.com">Service (systems architecture) Totally Explained</a>

Then simply click through this link from your web page. Our crawlers will verify your link, extract the title of your web page and instantly add a link back to it. If you like you can remove the words Totally Explained and embed the link in article text.
   As long as your link remains in place, we'll keep our link to you right here. Please play fair - our crawlers are watching. Your site must be closely related to this one's topic. Any kind of spamming, dubious practises or removing the link will result in your link from us being dropped and, potentially, your whole site being banned.



Copyright © 2007-8 totallyexplained.com | Licensed under the GNU Free Documentation License | Site Map
This article contains text from the Wikipedia article Service (systems architecture) (History) and is released under the GFDL | RSS Version